[UIPQB-85] Use non-id columns for queries #86
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ncovercash
requested review from
SergeYvas,
vashjs,
bvsharp and
mweaver-ebsco
mweaver-ebsco
approved these changes
Feb 23, 2024
vashjs
approved these changes
Feb 23, 2024
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira UIPQB-85
Purpose
We've extended FQL to support using non-ID columns in place of their normal IDs (e.g.
vendor_code/vendor_nameinstead ofvendor_id).This changes the query builder to:
idColumnNamevendor_idand map them tovendor_codesilently, to be saved upon edit.Note
The result viewer still shows an incorrect user friendly query for
vendor_codeand other derived columns, which must be converted on the backend. MODLISTS-85 has been created to fix this.